[PATCH] fusermount: Fix the close_range ifdef

This fixes commit 82bcd818
That commit had removed HAVE_LINUX_CLOSE_RANGE in meson generation,
but didn't remove the usage in fusermount.c - fusermount was then
not using the close_range syscall.

Closes: https://github.com/libfuse/libfuse/issues/1284
Signed-off-by: Bernd Schubert <bernd@bsbernd.com>
Gbp-Pq: Name Fix-the-close_range-ifdef.patch

[PATCH] conn->want conversion: Fix fuse_apply_conn_info_opts()

fuse_apply_conn_info_opts() was applying to 'want_ext',
which would cause conflicts with 'want' if the application
applied its own flags to 'conn->want'.

Solution is:
    - to move fuse_{set,unset,get}_feature_flag and
      convert_to_conn_want_ext() to fuse_lowlevel.c and
      to define them as part of the public API, although
      convert_to_conn_want_ext() should not be used - it is
      currently needed to be a public function due as it needs
      to be defined for the tests.

Related to https://github.com/libfuse/libfuse/issues/1171 and
https://github.com/libfuse/libfuse/pull/1172.

Closes: https://github.com/libfuse/libfuse/issues/1171
Signed-off-by: Bernd Schubert <bschubert@ddn.com>
Gbp-Pq: Name Fix-fuse_apply_conn_info_opts.patch

[PATCH] Add container_of and ROUND_UP macros

Needed by follow up commits. container_of is actually
just moved/consolidated to util.h.

Signed-off-by: Bernd Schubert <bschubert@ddn.com>
(cherry picked from commit c5a032b3410d7225ac0355355faa63565a209943)

Gbp-Pq: Name Add-container_of-and-ROUND_UP-macros.patch

[PATCH] Make conn->want/want_ext conversion non fatal

there are too many issues with conn->want and conn->want_ext
conversion, for now just log a warning, but setting both
flags is now not fatal anymore.

Signed-off-by: Bernd Schubert <bschubert@ddn.com>
Gbp-Pq: Name Make_conn-want-want_ext_conversion_non_fatal.patch

[PATCH] meson.build: make special_funcs check more reliable

Unfortunately while cross-compiling with build tools like Buildroot it
happens to have repeated flags or anything that could lead to a warning.
This way the check fails because of a warning not related to the special
function. So let's use cc.links() and increase minimum meson_version to
0.60 since cc.links() has been added during that version.

Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
Gbp-Pq: Name meson.build-make-special_funcs-check-more-reliable.patch

[PATCH] Fix meson function tests

Several meson tests were incorrectly failing

Checking for function "static_assert" : NO (cached)
Checking for function "pthread_setname_np" : NO (cached)
Check usable header "#include <linux/close_range.h>" : NO (cached)

These functions get now tested with compilation tests
and get found on my system.

Checking if "static_assert check" compiles: YES
Checking if "pthread_setname_np check" compiles: YES
Checking if "close_range check" compiles: YES

Signed-off-by: Bernd Schubert <bschubert@ddn.com>
Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
Gbp-Pq: Name Fix_meson_function_tests.patch

fuse3 (3.17.2-3) unstable; urgency=medium

  * Backport upstream fixes:
    - fix the close_range ifdef,
    - fix deadlock in truncate operation in memfs_ll.cc example.

[dgit import unpatched fuse3 3.17.2-3]

Import fuse3_3.17.2-3.debian.tar.xz

[dgit import tarball fuse3 3.17.2-3 fuse3_3.17.2-3.debian.tar.xz]

Import fuse3_3.17.2.orig.tar.gz

[dgit import orig fuse3_3.17.2.orig.tar.gz]